-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E2E_Tests_CI_FIX #85
E2E_Tests_CI_FIX #85
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left one question
src/env_vars.py
Outdated
@@ -26,7 +27,7 @@ def get_env_var(var_name, default=None): | |||
IP_RANGE = get_env_var("IP_RANGE", "172.18.0.0/24") | |||
GATEWAY = get_env_var("GATEWAY", "172.18.0.1") | |||
RUNNING_IN_CI = get_env_var("CI") | |||
API_REQUEST_TIMEOUT = get_env_var("API_REQUEST_TIMEOUT", 20) | |||
API_REQUEST_TIMEOUT = get_env_var("API_REQUEST_TIMEOUT", 50) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometimes I got error that REST isn't ready or connection timeout this could be my machine but I added it just to avoid it happening on CI but I can remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to remove this change as this could make the CI slow if we end up with a lot of requests timing out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
PR Details
This PR has 3 tests for E2E
1-test_filter_20_senders_1_receiver
NOTE: for NODE_2 = GO-WAKU 20 nodes also tested and works fine
2-test_filter_3_senders_multiple_msg_1_receiver
1- 4 nodes started with relay = true
2- node 4 is filter node
3- node5 makes filter request and marks node4 as filter node
4- 3 nodes publish messages_num*3 messages (each publish messages_num)
5- node 5 makes filter inquiry to get published messages
6. check is done to confirm receiving of messages_num messages
3-test_filter_many_subscribed_nodes
1- 2 nodes started with relay = true
2- node 2 is filter node
3- "max_subscribed_nodes" are created and making node2 as their filter node
4- node 1 publish message
5- the "max_subscribed_nodes" inquiry the published messages
6- check is done to ensure each node receives 1 message
NOTE: for NODE_2 = GO-WAKU "max_subscribed_nodes" nodes also tested and works fine
Additional changes
1- Adding flag --max-connections=1000 at file waku_node.py to increase number of connected peers
2- Adding var stress_enabled at env_vars.py when this var = true some limits in number of nodes will increase to allow
extensive testing
Issues reported: